Repository navigation
docs(tokens): approving a desktop app sign-in needs Create Token in any of your organizations - #1348
Conversation
…ny of your organizations Signed-off-by: Lee Calcote <lee.calcote@layer5.io>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
|
Preview deployment for PR #1348 removed. This PR preview was automatically pruned because we keep only the 6 most recently updated previews on GitHub Pages to stay within deployment size limits. If needed, push a new commit to this PR to generate a fresh preview. |
Fold the behavior corrections from the reverted Cloud restructure into the pages they originally covered, keeping their URLs, titles and structure. Re-apply later Cloud edits from #1281, #1286, #1326, #1335, #1337, #1338, #1339, #1340, #1341, #1342, #1343, #1348 and #1349. Remove unshipped claims from the Kanvas tutorials. Add aliases so URLs published during the restructure keep resolving. Signed-off-by: Mia Grenell <184569369+miacycle@users.noreply.github.com>
Approving a desktop app or CLI sign-in now checks Create Token in at least one organization you belong to, not the selected organization or the custom domain's organization. Companion to the layer5io/meshery-cloud fix for native sign-in on custom domains.
Summary by CodeRabbit